Table 6–1: 4GL exceptions for .NET proxies
|
Exception class
|
Description
|
|
|
Invalid URL format in the connection parameter.
|
|
|
AppServer communications error. The message contains the specific reason for the failure.
|
|
|
Attempt to use a session already in use by another client thread.
|
|
|
Error connecting to an AppServer. The base class of several specific exceptions.
|
|
|
Failed AppServer connection attempt. The message contains the specific reason for the failure.
|
|
|
Attempt to use an unknown or unsupported protocol.
|
|
|
Invalid NameServer host specified in the URL.
|
|
|
Invalid NameServer port specified in the URL.
|
|
|
An inconsistency was detected during meta data validation.
|
|
|
NameServer was not found at the specified port number.
|
|
|
Specified NameServer port was outside of the acceptable port range (minimum: 1024, maximum: 65535).
|
|
|
Attempt to contact NameServer exceeded the maximum retry count.
|
|
|
NameServer communications error. The message contains the specific reason for the failure.
|
|
|
NameServer communications broken. Either no response was received from the NameServer or the thread was interrupted before the response was received.
|
|
|
Invalid format for message received from NameServer.
|
|
|
Application Service specified in URL is unknown to the NameServer.
|
|
|
The root exception for all Open Client errors. Used for miscellaneous client-side errors.
|
|
|
Output DataSet/DataTable error; for example, trying to get a column value out of column order or to make an illegal type conversion.
|
|
|
The base class for all customer-visible Open Client errors.
|
|
|
4GL ERROR condition.
|
|
|
The base class for 4GL run-time errors.
|
|
|
4GL QUIT condition.
|
|
|
4GL STOP condition.
|
|
|
An inconsistency was detected during schema validation.
|
|
|
An unexpected error indicating an OpenEdge bug or an unusual environmental problem, such as running out of disk space.
|
|
|
AppService host name is unknown.
|